Method and apparatus for interactive remote viewing and collaboration of dental images

ABSTRACT

A method of dental restoration treatment utilizing the electronic delivery of an electronic model image of the dental restoration treatment. The method includes generating an electronic model image of a proposed dental restoration treatment; storing the electronic model image within computer readable memory of a server-based computing system; delivering the electronic model image to a doctor having a remote client computer over a distributed communications network; and displaying the electronic model image upon the remote client computer and performing analysis of the electronic model image. The doctor is provided with a variety of viewing and analysis tools, and can add notations to the electronic model image.

CROSS REFERENCE TO RELATED APPLICATION

This is a continuation-in-part of application Ser. No. 09/846,037, filedon Apr. 29, 2001, currently pending, the entire disclosure of which ishereby incorporated by reference.

TECHNICAL FIELD

The invention relates generally to a distributed computing system forthe creation and distribution of electronic models of objects and moreparticularly to a system, method and article of manufacture fordelivering and manipulating electronic model images to end users using adistributed computing system.

BACKGROUND

Computational resources available for use by various end users ofcomputing systems has increased significantly. This increase incapability of systems has created the ability for many more end users toutilize computer based image systems to replace processes that utilizepaper and physical model processes. In the past, computer aided design,drafting, and manufacture (CAD/CAM) tools represented an area ofapplications in which computer based image systems have migrated frompaper and model based processes to electronic systems.

These CAD/CAM systems typically consist of design and drafting toolsthat allow technical designers to build systems that were previouslydesigned on paper using draftsmen. Over time, the computing system andtheir respective tools have allowed increasing interactive manipulationof components during the design process. This advance in design of itemsthat are then manufactured has occurred using these computer aidedsystems.

These CAD/CAM systems, however, typically start their processes with aset of pre-defined libraries of components that may be used by the userof the computing system. For example, electronic schematics possess alibrary of components that are used to specify a circuit and its layout.The creation of these libraries, as well as the amount of computationalresources needed to perform the operations related to these systems, hasprevented the wide-spread use of these systems in other areas oftechnology.

With the advances recently made in computational systems, these computerbased image systems may be used to permit end users to replace paper andphysical models with electronic images. Two areas of technology presentadditional obstacles to the more widespread use of these systems. First,a mechanism to capture image representations of physical objectsaccurately and with sufficient resolution is needed in a form that isboth inexpensive to operate while providing rapid turn-around for users.Second, a mechanism to easily transmit the images to end users from thelocation where the image representation of physical objects aregenerated is also needed. Neither of these latter obstacles has beenovercome in existing imaging systems.

SUMMARY

The present invention relates to a method, apparatus, and article ofmanufacture for delivering and manipulating electronic model images toend users using a distributed computing system.

In one aspect of the invention, a method for providing electronicdelivery of an electronic model image of a dental restoration treatmentis provided. The method comprises generating an electronic model imageof a proposed dental restoration treatment, storing the electronic modelimage within computer readable memory of a server-based computingsystem, delivering the electronic model image to a doctor having aremote client computer over a distributed communications network, anddisplaying the electronic model image upon the remote client computerand performing analysis of the electronic model image.

In one embodiment, notations can be added to the electronic model imageto allow the doctor to comment on, and suggest changes to, the dentalrestoration treatment. The electronic model image with the attachednotations can then be transmitted to a laboratory to make any necessarycorrections to the image or to begin fabrication of the dentalrestoration.

In another aspect of the invention, a method of dental restorationtreatment is provided. The method comprises displaying an electronicmodel image of a proposed dental restoration treatment upon a displaydevice, performing an analysis of the electronic model image todetermine whether or not the proposed dental restoration treatment isappropriate, and attaching a notation to the electronic model image thatis displayed.

These and various other advantages and features of novelty whichcharacterize the invention are pointed out with particularity in theclaims annexed hereto and form a part hereof. However, for a betterunderstanding of the invention, its advantages, and the objects obtainedby its use, reference should be made to the drawings which form afurther part hereof, and to accompanying descriptive matter, in whichthere are illustrated and described specific examples of an apparatus inaccordance with the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a distributed computing system for the creation anddistribution of electronic models of objects according to one embodimentof the present invention.

FIG. 2 illustrates an exemplary computing system useful for implementingan embodiment of the present invention.

FIG. 3 illustrates an eModel generation system according to anembodiment of the present invention.

FIG. 4 illustrates an eModel for an impression of a patient's mouth andteeth according to yet another example embodiment of the presentinvention.

FIG. 5 illustrates an eModel for a shell from a cellular telephone caseaccording to yet another example embodiment of the present invention.

FIG. 6 illustrates a block diagram for an eModel generation anddistribution system according to an embodiment of the present invention.

FIG. 7 illustrates a block diagram for an eModel generation processaccording to yet another example embodiment of the present invention.

FIGS. 8 a-b illustrate an example of an object from which an eModel isgenerated according to yet another example embodiment of the presentinvention.

FIG. 9 illustrates a representation of the object in FIG. 8 using apolygonal mesh according to an embodiment of the present invention.

FIG. 10 illustrates a simplified representation of the object in FIG. 8using a reduced polygonal mesh according to yet another exampleembodiment of the present invention.

FIG. 11 illustrates a format for an eModel data file according to yetanother example embodiment of the present invention.

FIG. 12 illustrates an eModel data server system according to yetanother an embodiment of the present invention.

FIG. 13 illustrates another eModel data server system according to yetanother example embodiment of the present invention.

FIG. 14 illustrates an eModel for an impression of a patient's mouthaccording to yet another example embodiment of the present invention.

FIGS. 15 a-b illustrate use of an eModel to determine spatialmeasurements corresponding to distances in a patient's mouth accordingto an embodiment of the present invention.

FIGS. 16 a-b illustrate manipulating positions of patient's teeth usingan eModel according to yet another example embodiment of the presentinvention.

FIGS. 17 a-c illustrate combining an eModel of a patient's teeth with anx-ray according to yet another example embodiment of the presentinvention.

FIG. 18 illustrates processing modules used to implement an eModel dataserver according to an embodiment of the present invention.

FIG. 19 illustrates an operational flow for the processing performedwithin an eModel data server according to yet another example embodimentof the present invention.

FIG. 20 illustrates processing modules used to implement an end userclient computer according to yet another example embodiment of thepresent invention.

FIG. 21 illustrates an operational flow for the processing performedwithin an end user client computer according to yet another exampleembodiment of the present invention.

FIGS. 22-26 illustrate end user display screens on an end user clientcomputer for use in viewing and manipulating a dental restoration eModelaccording to an embodiment of the present invention.

FIG. 27 illustrates an operational flow of an exemplary dentalrestoration treatment process using the dental restoration eModel.

DETAILED DESCRIPTION

The present invention relates to a code generation method, apparatus,and article of manufacture for providing a distributed computing systemfor the creation and distribution of electronic models of objects.

FIG. 1 illustrates a distributed computing system for the creation anddistribution of electronic models of objects according to one embodimentof the present invention. End users operate a plurality of differentcomputing systems 110-113 to perform their respective computing tasks.End users typically use one general purpose computing system for avariety of tasks. Accordingly, to insure the practicality and adoptionof an imaging system designed to replace paper and model based systems,the imaging system used by end users 110-113 preferably consists oflaptop and/or desktop style personal computers.

These computing systems typically possess a mechanism to communicatewith other computing systems over a communications network 101. TheInternet 101, as a publicly available communications network, providesan available communications path between virtually any two computingsystems after they first connect to the Internet. While othercommunications mechanisms exist and may be used, the Internet provides awell-known mechanism to communicate data between two computing systems.

In an image-based eModel system, an end user 110 communicates over acommunications network 101 to a server 121 to retrieve electroniceModels from a database 122. The end user 110 may be located anywhere aconnection to the communications network 101 exists to retrieve theeModels from the database 122. This database 122 may be located withinan eModel data server system 102 that is maintained by third partiesthat provide maintenance, data back up, and similar data processingoverhead functions that are not an overriding concern for an end user.This data back-up, for example, may consist of long-term archiving ofdata to replace maintenance of physical models that have in the pastrequired a great deal of effort and expense to complete.

The eModels themselves consist of a data file stored on the server 121in a database 122 that allows quick and efficient access for users.These eModels are generated in a separate eModel generation system 103that consists of one or more model scanning units 131-134. These units131-134 are connected together using a local communications network 136and a communications path 135 to the Internet 101. As such, eModels,once generated may be transferred to the eModel Data server system 102for ultimate use by end users 110-113.

With reference to FIG. 2, an exemplary system for implementing theinvention includes a general-purpose computing device in the form of aconventional personal computer 200, including a processor unit 202, asystem memory 204, and a system bus 206 that couples various systemcomponents including the system memory 204 to the processor unit 202.The system bus 206 may be any of several types of bus structuresincluding a memory bus or memory controller, a peripheral bus and alocal bus using any of a variety of bus architectures. The system memoryincludes read only memory (ROM) 208 and random access memory (RAM) 210.A basic input/output system 212 (BIOS), which contains basic routinesthat help transfer information between elements within the personalcomputer 200, is stored in ROM 208.

The personal computer 200 further includes a hard disk drive 212 forreading from and writing to a hard disk, a magnetic disk drive 214 forreading from or writing to a removable magnetic disk 216, and an opticaldisk drive 218 for reading from or writing to a removable optical disk219 such as a CD ROM, DVD, or other optical media. The hard disk drive212, magnetic disk drive 214, and optical disk drive 218 are connectedto the system bus 206 by a hard disk drive interface 220, a magneticdisk drive interface 222, and an optical drive interface 224,respectively. The drives and their associated computer-readable mediaprovide nonvolatile storage of computer readable instructions, datastructures, programs, and other data for the personal computer 200.

Although the exemplary environment described herein employs a hard disk,a removable magnetic disk 216, and a removable optical disk 219, othertypes of computer-readable media capable of storing data can be used inthe exemplary system. Examples of these other types of computer-readablemediums that can be used in the exemplary operating environment includemagnetic cassettes, flash memory cards, digital video disks, Bernoullicartridges, random access memories (RAMs), and read only memories(ROMs).

A number of program modules may be stored on the hard disk, magneticdisk 216, optical disk 219, ROM 208 or RAM 210, including an operatingsystem 226, one or more application programs 228, other program modules230, and program data 232. A user may enter commands and informationinto the personal computer 200 through input devices such as a keyboard234 and mouse 236 or other pointing device. Examples of other inputdevices may include a microphone, joystick, game pad, satellite dish,and scanner. These and other input devices are often connected to theprocessing unit 202 through a serial port interface 240 that is coupledto the system bus 206. Nevertheless, these input devices also may beconnected by other interfaces, such as a parallel port, game port, or auniversal serial bus (USB). A monitor 242 or other type of displaydevice is also connected to the system bus 206 via an interface, such asa video adapter 244. In addition to the monitor 242, personal computerstypically include other peripheral output devices (not shown), such asspeakers and printers.

The personal computer 200 may operate in a networked environment usinglogical connections to one or more remote computers, such as a remotecomputer 246. The remote computer 246 may be another personal computer,a server, a router, a network PC, a peer device or other common networknode, and typically includes many or all of the elements described aboverelative to the personal computer 200. The network connections include alocal area network (LAN) 248 and a wide area network (WAN) 250. Suchnetworking environments are commonplace in offices, enterprise-widecomputer networks, intranets, and the Internet.

When used in a LAN networking environment, the personal computer 200 isconnected to the local network 248 through a network interface oradapter 252. When used in a WAN networking environment, the personalcomputer 200 typically includes a modem 254 or other means forestablishing communications over the wide area network 250, such as theInternet. The modem 254, which may be internal or external, is connectedto the system bus 206 via the serial port interface 240. In a networkedenvironment, program modules depicted relative to the personal computer200, or portions thereof, may be stored in the remote memory storagedevice. It will be appreciated that the network connections shown areexemplary, and other means of establishing a communications link betweenthe computers may be used.

Additionally, the embodiments described herein are implemented aslogical operations performed by a computer. The logical operations ofthese various embodiments of the present invention are implemented (1)as a sequence of computer implemented steps or program modules runningon a computing system and/or (2) as interconnected machine modules orhardware logic within the computing system. The implementation is amatter of choice dependent on the performance requirements of thecomputing system implementing the invention. Accordingly, the logicaloperations making up the embodiments of the invention described hereincan be variously referred to as operations, steps, or modules.

FIG. 3 illustrates an eModel generation system according to anembodiment of the present invention. The eModel generation system 103 isan object scanning facility having one or more model scanner units131-134 that scan user objects 300 using a laser scanner 310 that mountsthe user object 300 on a multi-axis scanning platform 311. The laserscanner 310 interfaces with one or more programmable processing devices321-322 to process the laser scanner data into usable object image data.These model scanner units 131-134 are connected together using a datacommunications network 136 to permit the image data to be transferredbetween processing devices. Ultimately, the eModel data is transferredto a data server 102 over a communications network 101 like theInternet.

In one embodiment, each model scanner unit 132 includes two processingdevices 321-322 to process the laser scanner data and generate the modelimage data. In this embodiment, the processing utilizes one suchcomputing device 321 to processing the scanner data to generate apolygonal mesh of triangles and utilizes a second computing system 322to further process the initial polygonal mesh into a reduced set ofsurfaces that may be ultimately used by an end user. One skilled in theart will recognize that these two computing devices may in fact beconstructed using any number of programmable computing devices where thecomputing capacity of the devices used will determine the amount of timeneeded to complete a given processing task. As such, other embodimentsof the present invention may be used for these computing devices withoutdeviating from the spirit and scope of the present invention as recitedwithin the attached claims.

In a preferred embodiment, the laser scanner 310 is a line scanner ofthe type made by Laser Design, Incorporated of Bloomington Minn., ModelNo. RPS-120. The scanner possesses a capability to transfer data to acomputing system 321 at a rate of 14,400 data points per second and havea resolution of 12 microns. In order to create adequate eModels for useritems, the scanner 310 possesses a volumetric accuracy of approximately25 microns. The multi-axis platform 311 rotates the user item 300 withinthe field of view of the laser scanner 310 in order to collectsufficient data points from all orientations to observe the entiresurface of the user object 300.

FIG. 4 illustrates an eModel for an impression of a patient's mouth andteeth according to yet another example embodiment of the presentinvention. In this example, an impression of a patient's mouth and teethare obtained from a dental care provider. From the impression, a plastermodel of the upper and lower teeth are obtained. These models have beentypically used by dental care providers to observe and measure apatient's mouth and teeth when planning how a course of dental caretreatment is to progress. According to the present invention, theplaster model is scanned in the eModel generation system 103 to generatethe upper 402 and lower 401 eModels that correspond to a digital imagerepresentation of the plaster model.

Once the digital eModel is obtained, the plaster model is no longerneeded. As such, the storage of the model is no longer required bydental care providers, as has been the case for most of the pastpractices of dental care providers. Because the eModel is a digitalrepresentation of the physical model, a plurality of user controls411-412 are used by the end user to view the user item 300, in this casethe patient's teeth 401-402, from any orientation. Measurements andother manipulations of the eModel are also permitted.

FIG. 5 illustrates an eModel for a shell from a cellular telephone caseaccording to yet another example embodiment of the present invention. Inthis second example, a shell from a cellular telephone 501 correspondsto the user item 300 that is scanned to generate an eModel. Any useritem 300 that is small enough to fit within the scanning space of thescanner 310 and multi-axis platform 311 in the eModel generation system103 may be used to generate an eModel. In the preferred embodiment, theuser item is less than a 6-inch volumetric cube. One skilled in the artwill recognize that other scanning devices that produce scanned imagedata at a sufficiently small resolution that permits larger items to bescanned may also be used without deviating from the spirit and scope ofthe present invention as recited within the attached claims. Inaddition, the nature and shape of the user item 300, whether itcorresponds to a model of a patient's mouth and teeth or corresponds toa component of an item of manufacture, does not change the operation ofthe present invention as recited within the attached claims.

FIG. 6 illustrates a block diagram for an eModel generation anddistribution system according to an embodiment of the present invention.The process starts 601 and an eModel is generated from a scan of an enduser item in module 611. Once the eModel is generated, the model isstored within a data storage medium on a remotely accessible server inmodule 612. Next, an end user receives an eModel of interest for use onhis or her client computer over a communications network in module 613.

Once an end user receives the eModel, the end user may view andmanipulate the eModel as needed to complete any planning, analysis andsimilar operations in module 614. Test module 615 determines if a neweModel has been created as part of the end user's manipulation of aneModel and if the newly created eModel should be saved for later use. Ifthe new eModel exists and is to be saved, module 616 saves the eModellocally on the end user client computer for later use and the processingends 602. If test module 615 determines that a new eModel is not to besaved, the processing also ends 602.

FIG. 7 illustrates a block diagram for an eModel generation processaccording to yet another example embodiment of the present invention.The process for generating an eModel of a user item 300 starts when ascan module 701 utilizes a scanner 310 to generate a point cloud datafile 711. For objects that typically fit within the 6 inch volumetriccube of the scanner, this point cloud data file 711 may comprisesbetween 2 and 3 million data points. The large amount of data pointsgenerated from the scan of a single user item 300 has posed asignificant limitation upon the use of eModels in the past. In thepreferred embodiment, the scanning process implemented in the scanmodule 701 is performed within the first of two programmable processors321 within a given model scanner unit 132.

The point cloud data file 711 represents a data point for each locationon the surface of the user item 300. The file is processed into apolygonal mesh of triangles in a mesh module 702. In this process, thepoints from the point cloud data file are organized into triangles ofneighboring points that describe the surface of the user item 300 thathas been scanned. The creation of a polygonal mesh data file 712 thatcontains the specification of all of the triangles reduces the amount ofdata to between 100-300 k triangles.

The number of triangles that are used to describe a surface of the useritem 300 may be reduced further in a filtering module 703 when a reducedpolygonal mesh file 713 is created. This reduction of the number oftriangles is accomplished when adjacent triangles are sufficientlyco-planer to permit the surface described by two or more triangles to besimilarly described using a single triangle. The reduced polygonal meshdata file 713 typically consists of 60 k triangles that permits amanageable amount of data to be used when eModels are processed.

The eModel are completed by an eModel transfer module 704 that attachesa file header that describes the user item in sufficient detail that itmaybe retrieved at a later date. The eModel is contained within aneModel data file 714 that may be transmitted over the Internet 101 tothe eModel data server for storage within its database.

FIG. 8 a-b illustrate an example of an object from which a eModel isgenerated according to yet another example embodiment of the presentinvention. A simple geometric 3D shape 801 is presented as an example ofhow a reduced polygonal mesh is generated that may be used as an eModel.This shape 801 has two visible faces: a small triangular side face 812and a larger rectangular face 811. Three other faces make up this simpleobject that are not visible from the perspective shown in FIG. 8 a.

FIG. 8 b shows this object 801 having a set of surface data pointssuperimposed upon the object 801 faces. When a laser line scanner passesits sensor over a face of the object 801, a line of points correspondingto the position of the objects' surface are obtained. These points areseparated by the spatial resolution of the scanner. The data points, P0821 are specified using a 3 coordinate position X0, Y0, Z0. As theobject 801 is moved within the scanning area of the multi-axis platform,the scanner translates the data points to a common coordinate systemsuch that the collection of all points represents the points in a 3Dcoordinate system that corresponds to the surface of the item 801. Thesedata points are contained within the point cloud data file 711 that isgenerated by the scan module 701.

FIG. 9 illustrates a representation of the object in FIG. 8 using apolygonal mesh according to an embodiment of the present invention. Asdiscussed above, the point cloud data file 711 is reduced to a polygonalmesh of triangles in which the surface of the triangles are used toapproximate the surface of the item 801. In this example, a triangle, T1900, is located on the larger surface 811 of the item 801. The triangleT1 900 is specified using the three corner points P0 901, P1 902, and P2903. As before, each of these three points are specified using a 3Dcoordinate system such that T1 900 is defined:

-   -   T1: {P0, P1, P2} or    -   T1: {[X0, Y0, Z0], [X1, Y1, Z1], {[X2, Y2, Z2]}.

Each triangle in the polygonal mesh is specified using the three pointsas shown above. No particular order for the points making up thetriangle is necessary. The smaller side 812 of the item 811 in thisexample is initially shown with six triangles 911-916. The triangles inthe polygonal mesh may be created using any number of well known methodsfor reducing point position data into a polygonal mesh that approximatesthe surface of the object.

FIG. 10 illustrates a simplified representation of the object in FIG. 8using a reduced polygonal mesh according to yet another exampleembodiment of the present invention. A reduced polygonal mesh isgenerated by combining adjacent triangles in the original polygonal meshwhen the two or more triangles are sufficiently coplanar that they maybe represented using a single triangle. In this example, a large numberof small triangles may have been originally generated on the mesh shownin FIG. 9. When a flat surface of the simple object 801 is considered,the number of triangles needed is reduced significantly 1001-1007. Inthe example, all of the small triangles from the small side 812 of theitem 801 have been combined into a single triangle 1011. The processingassociated with this filtering operation controls the amount of trianglecombinations by setting a threshold relating to the minimum amount ofdeviation from a single plane for the two or more triangles that ispermitted before two or more triangles are required to remain separate.This filtering process may be accomplished using a number ofcommercially available polygonal mesh processing products withoutdeviating from the present invention as recited within the attachedclaims.

FIG. 11 illustrates a format for an eModel data file according to yetanother example embodiment of the present invention. The eModel datafile consists of a file header info block 1101 and a trianglespecification block 1102. The triangle specification block consists ofthe set of triangle definitions 1111-1113 that are used to define thereduced polygonal mesh. The file header info block 1101 includes a setof searchable identification information that may be used to identify aparticular model from any number of related models. The mouth and teetheModels, for example, will likely contain patient identificationinformation such as name, date of birth, address, social security numberthat may be used to uniquely identify the patient from which the modelwas generated. The info block 1101 may also contain dental care providerinformation such as the dentist name and address as well as the date onwhich the impression was taken that generated the eModel.

For other items, such as the cellular phone shown in FIG. 5, any usefulidentifying information may be used. This data is typically ASCIIencoded data that may be easily searched and processed as necessary. Oneskilled in the art will recognize how this file header info block 1101may be modified to include any information needed by a particularapplication without deviating from the spirit and scope of the presentinvention as recited within the attached claims.

FIG. 12 illustrates an eModel data server system according to anembodiment of the present invention. The eModel data server 102communicates with the eModel generation system 103 and end users 110over a communications network 101. The eModels that are generated aretransmitted to the eModel data server 102 for storage in its databases1204-1205 for later user.

The eModel data server 102 includes a communications server module 1201,a database server module 1203, and an eModel storage server module 1202to perform its tasks. The communications server module 1201 performs thecommunications functions needed to receive eModels from the generationsystem 103 as well as the communication functions needed to interactwith end users when they wish to locate and download eModels ofinterest.

The eModels received from the generation system 103 are stored withintwo databases. A copy of the file header info block 1101 is storedwithin a first database 1204 and the entire eModel file is stored withina file storage database 1205. This separation allows the file headerinfo block data to be stored within a relational database to permitrapid searching for eModels of interest. Once the identity of a desiredeModel is located in the relational database 1204, the end user mayrequest a copy of the larger eModel file from the file storage database1205. This separation of the two database functions allows the datastorage and data processing requirements of each operation to be scaledindependently of each other as the nature of the end user interactionwith the server is determined. If significant amounts of database queryoperations are occurring in a particular use of the server, theprocessing capabilities of the relational database may be increased. Ifthe server is predominantly used to transfer large eModel files tousers, data transfer capacity of the file storage database may beincreased.

FIG. 13 illustrates another eModel data server system according to yetanother example embodiment of the present invention. In this particularembodiment, the communication server 1201, the eModel header databaseserver 1203, and the eModel file storage server 1202 are all connectedto a common local area network to perform the data communicationoperations. A firewall server 1312 connects the local area network tothe Internet 101 for communications to end users 110 and the eModelgeneration system 103.

The eModel file header info block database 1204 is connected to theeModel header database server 1203 to provide the relational databasefunctions needed to locate eModels of interest. The eModel database 1205is connected to the eModel file storage server 1202 to provide the filestorage for all of the eModels.

Within the communications server 1201, a command and control module 1301receives requests for operations and coordinates the processing of theother modules and servers to complete a processing and data retrievalrequest. A client interface module 1303 processes the entirecommunication request received from an end user 110. The eModelgeneration interface module 1302 processes all of the communicationrequests from the eModel generation system 103 to accept and store neweModels within the databases 1204-1205.

In order to perform its processing functions, the communications server1201 receives the command messages listed in Table 1. These commandsallow eModels to be stored into the databases 1204-1205 and allow endusers 110 to search for and retrieve eModels from the databases. TABLE 1Server Communication Commands Procedure Parameters Return Descriptionuser_get_emodel_list USER_LOGIN_NAME, E_MODEL_ID, get emodelUSER_PASSWORD, PATIENT_LAST_NAME, META data BEGIN_DATE, END_DATEPATIENT_FIRST_NAME, between CREATION_DATE BEGIN_DATE and END_DATElab_get_user_list USER_LAST_NAME, USER_LOGIN_NAME, get a list of allUSER_FIRST_NAME, USER_TITLE, data for USER_ADDRESS_CITY, USER_LAST_NAME,specified user USER_ADDRESS_STATE, USER_FIRST_NAME,USER_ORGANIZATION_NAME USER_MIDDLE_NAME, USER_ADDRESS_CITY,USER_ADDRESS_STATE, USER_ORGANIZATION_NAME add_labLAB_ORGANIZATION_NAME, none create a lab LAB_LAST_NAME, entry in theLAB_FIRST_NAME, SQL database LAB_MIDDLE_NAME, LAB_TITLE, LAB_PHONE,LAB_FAX, LAB_E_MAIL, LAB_ADDRESS_STREET_1, LAB_ADDRESS_STREET_2,LAB_ADDRESS_STREET_3, LAB_ADDRESS_CITY, LAB_ADDRESS_STATE,LAB_ADDRESS_COUNTRY, LAB_ADDRESS_ZIP, LAB_LOGIN_NAME, LAB_PASSWORDadd_iris_user USER_ORGANIZATION_NAME, none create a user USER_LAST_NAME,account in the USER_FIRST_NAME, SQL database USER_MIDDLE_NAME,USER_TITLE, USER_PHONE, USER_FAX, USER_E_MAIL, USER_BULK_MAIL,USER_ADDRESS_STREET_1, USER_ADDRESS_STREET_2, USER_ADDRESS_STREET_3,USER_ADDRESS_CITY, USER_ADDRESS_STATE, USER_ADDRESS_COUNTRY,USER_ADDRESS_ZIP, USER_LOGIN_NAME, USER_PASSWORD add_scanner LAB_ID,none create a ELECTRICAL_DRAWING, scanner entry ELECTRICAL_BOM, in theSQL MECHANICAL_DRAWING, database MECHANICAL_BOM add_scanner_serv_recSCANNER_ID, LAB_ID, none create a SCANNER_CALIBRATED, scannerSCANNER_MAINTENANCE, service record SCANNER_REPAIRED, entry in theSCANNER_GAGE_SN, SQL database SCANNER_GAGE_NIST, SCANNER_LASER_SN,SERVICE_START_DATE, SERVICE_FINISH_DATE, SERVICE_DESCRIPTION,SERVICE_TECHNICIAN add_emodel E_MODEL_ID, none create anUSER_LOGIN_NAME, emodel record SCANNER_ID, in the SQL USER_DESCRIPTION,database LAB_DESCRIPTION, PATIENT_LAST_NAME, PATIENT_FIRST_NAME,PATIENT_MIDDLE_NAME, PATIENT_TITLE, PATIENT_BIRTHDATE, PATIENT_ID,PATIENT_SEX, PATIENT_RACE, OPTION_FIELD, FILESERV_NAME, CREATION_DATEget_all_user_info USER_LOGIN_NAME, USER_ORGANIZATION_NAME, retrieve aUSER_PASSWORD USER_LAST_NAME, listing of all USER_FIRST_NAME,information USER_MIDDLE_NAME, for specified USER_TITLE, USER_PHONE, userUSER_E_MAIL, USER_BULK_MAIL, USER_ADDRESS_STREET_1,USER_ADDRESS_STREET_3, USER_ADDRESS_CITY, USER_ADDRESS_STATE,USER_ADDRESS_COUNTRY, USER_ADDRESS_ZIP get_all_lab_info LAB_LOGIN_NAME,LAB_ORGANIZATION_NAME, retrieve a LAB_PASSWORD LAB_LAST_NAME, listing ofall LAB_FIRST_NAME, information LAB_MIDDLE_NAME, for specifiedLAB_TITLE, LAB_PHONE, lab LAB_E_MAIL, LAB_BULK_MAIL,LAB_ADDRESS_STREET_1, LAB_ADDRESS_STREET_3, LAB_ADDRESS_CITY,LAB_ADDRESS_STATE, LAB_ADDRESS_COUNTRY, LAB_ADDRESS_ZIP update_user_infoUSER_ID, none update USER_ORGANIZATION_NAME, information forUSER_LAST_NAME, specified user USER_FIRST_NAME, USER_MIDDLE_NAME,USER_TITLE, USER_PHONE, USER_FAX, USER_E_MAIL, USER_BULK_MAIL,USER_ADDRESS_STREET_1, USER_ADDRESS_STREET_2, USER_ADDRESS_STREET_3,USER_ADDRESS_CITY, USER_ADDRESS_STATE, USER_ADDRESS_COUNTRY,USER_ADDRESS_ZIP, USER_LOGIN_NAME, OLD_PASSWORD, NEW_PASSWORDupdate_lab_info LAB_ID, none update LAB_ORGANIZATION_NAME, informationfor LAB_LAST_NAME, specified lab LAB_FIRST_NAME, LAB_MIDDLE_NAME,LAB_TITLE, LAB_PHONE, LAB_FAX, LAB_E_MAIL, LAB_ADDRESS_STREET_1,LAB_ADDRESS_STREET_2, LAB_ADDRESS_STREET_3, LAB_ADDRESS_CITY,LAB_ADDRESS_STATE, LAB_ADDRESS_COUNTRY, LAB_ADDRESS_ZIP, LAB_LOGIN_NAME,OLD_PASSWORD, NEW_PASSWORD auth_emodel_retv USER_LOGIN_NAME, E_MODEL_ID,FILESERV_IP, determine USER_PASSWORD, FILESERV_PORT whether userE_MODEL_ID or AUTHORIZATION DENIED owns specified emodel auth_loginUSER_LOGIN_NAME, PASSWORD_INCORRECT, or determine USER_PASSWORDAUTHORIZED, or whether user LOGIN_NAME_INCORRECT account exists,password correct

FIG. 14 illustrates an eModel for an impression of a patient's mouthaccording to yet another example embodiment of the present invention. Inthis example, the upper portion of the eModel 402 has beenelectronically moved and placed in its position above the lower portionof the eModel 401. The plaster models typically used in the dental careindustry includes a base that allows easy spatial registration of thetwo portions of the eModel. This registration allows an end user tomanipulate the parts of the eModel to observer and determine how theindividual teeth interact as the two parts move together and apart fromeach other. The end user 110 may manipulate the eModel by moving,rotating and zooming to a perspective of interest.

FIGS. 15 a-b illustrate use of an eModel to determine spatialmeasurements corresponding to distances in a patient's mouth accordingto an embodiment of the present invention. In FIG. 15 a, a zoomed viewof a lower portion of the eModel 401 is shown in which individualspatial measurements of a tooth 1501 is determined by a user visuallymarking a first side of a tooth 1502 using an input device such as amouse and/or a trackball. Next the end user marks a second side 1503 ofthe tooth 1501 and the end user client system determines the distancebetween the two points as measured on the eModel polygonal mesh surface.This process may be repeated as many times as desired. In the past, thedental plaster model would be measured to obtain these values. The enduser system may automatically calculate this information, moreaccurately without the need to maintain and use the physical models oncea eModel has been scanned, generated and saved.

FIG. 15 b illustrates a similar set of spatial measurements beingobtained for a series of teeth 1531 on the lower portion of the model401 as well as a series of teeth 1532 on the upper portion of the model402. These measurements 1531-1532 are typically used by dental careproviders to determine a series of calculated values 1541 associatedwith the parabolic shape of a patient's mouth and teeth. The end usersystem may determine these values automatically from the spatial datameasured by an end user that in the past would have required asignificant amount of effort to obtain the measurements 1511-1512 andthen calculate the values 1513.

FIGS. 16 a-b illustrate manipulating positions of patient's teeth usingan eModel according to yet another example embodiment of the presentinvention. End users may be able to perform desired functions uponeModels that were difficult, or possibly impossible, to be performedupon physical models. FIG. 16 a illustrates an upper portion of aneModel of a patient's teeth and mouth from a physical model obtainedbefore dental treatment is performed. In this example, the dental careprovider wishes to move the location of a number of teeth to betteralign them with the parabolic arc that human teeth are typicallyaligned. The dental care provider, as an end user of the system, selectsand manipulates the location of three upper teeth 1601-1603 from acurrent position to a desired position.

The end user interactively moves portions of the eModel that representthe desired teeth to a new position. The dental care provider may removeteeth to determine spacing of the remaining teeth as a course oftreatment for a patient is created. All of the possible variations ontreatment options may be explored using the eModel until a desiredcourse of treatment is determined.

FIG. 16 b illustrates a different view for the eModel after the topfront teeth 1601-1602 have been moved as shown in FIG. 16 a. A neweModel for an item, such as the dental models, may be created throughthe modification of an existing eModel. Once the new model exists, itmay be viewed and manipulated in the same manner as any other eModel.Thus the various possible views of the original eModel may be viewedonce a new eModel has been created. In addition, an end user may togglebetween the two models to illustrate a before and after view of theteeth in light of a proposed treatment plan. All of this treatmentplanning which has occurred with physical models and paper and pencilcalculations may now be performed using the end user computing system.

FIGS. 17 a-c illustrate combining an eModel of a patient's teeth with anx-ray according to yet another example embodiment of the presentinvention. Even more significant than the simple manipulation ofeModels, new types of eModels can be created that combine more than oneform of digital image data to create a composite digital representationof patient data. FIG. 17 a illustrates a combination of a scanned eModelof a patient's teeth 401-402 that has been combined with a correspondingx-ray image 1701 for the patient. In this example, a profile of theentire scull is viewed in the x-ray image 1701. The two digital modules,for the teeth 401-402 and for the x-ray 1701, both typically possesscommon reference points from the tips of various teeth and similarstructures. When these common points are identified in both models, theprocessing system can register and scale the two models to permit thecombination of these two different models into a single module.

Like above, once a new eModel is created, the new eModel may itself bemanipulated. FIG. 17 b illustrates the movement of a patient's lower jawand teeth about the lower jaw pivot point 1711. As this movement occurs,the upper portion of the teeth eModel 402 and the lower portion of theteeth eModel 401 may be observed. As such, additional considerations maybe viewed while a treatment plan is determined for a patient.

FIG. 17 c further illustrates the possible options as the compositeeModel 1701 has been rotated to display more of a frontal view of theteeth eModels 401-402 in combination with the x-Ray. One skilled in theart will recognize that numerous variations on the types of x-rays andother digital image data, including but not limited to digitalphotographs and textual annotation, that may be combined with scannedeModels to obtain an image based eModel-processing system withoutdeviating from the spirit and scope of the present invention as recitedwithin the attached claims.

FIG. 18 illustrates processing modules used to implement an eModel dataserver according to an embodiment of the present invention. As discussedin FIG. 13, the eModel server includes a communications server 1201 thathas a client interface module 1303, an eModel generation interfacemodule 1302, and a command and control-processing module 1301. Inaddition, the communications server 1201 includes a data communicationsinterface module 1802 to perform processing functions needed to send andreceive data communications to and from other processing modules overthe local area network 1831. The command and control processing module1301 receives requests for data operations and interacts with either adatabase I/O processing module 1803 or an eModel file I/O processingmodule 1804 to complete the processing. The database I/O processingmodule 1803 is responsible for all database query requests that occurwhen end users search for eModels of interest. The database I/Oprocessing module 1803 also is responsible for storing new informationinto the relational database. The eModel file I/O processing module 1804is responsible for storing eModels into the file storage database andfor transferring stored eModels to end users.

The client interface module 1301 consists of an end user authenticationmodule 1811, a database query module 1812, and a file transfer module1813. The end user authentication module 1811 processes all end userattempts to log into the server to search for and access eModels. Thedatabase query module 1812 processes all incoming search requests togenerate and process relational database queries to locate matchingeModels based upon file header info data. The file transfer module 1813processes all eModel transfer requests to send eModels to end-users.

The eModel generation interface module 1302 processes all commands tostore new eModels generated in the eModel generation system into thedata server. The eModel generation interface module 1302 includes aheader extraction module 1821, a database storage module 1822, and afile server storage module 1823 to complete its functions. The headerextraction module 1821 extracts the file header info data from incomingeModels and formats them for insertion into the relational database. Thedatabase storage module 1822 stores the formatted header data into therelational database as needed to permit easy and efficient searches. Thefile server storage module 1823 performs the operations needed to storethe eModels into the file storage server.

FIG. 19 illustrates an operational flow for the processing performedwithin an eModel data server according to yet another example embodimentof the present invention. The process starts 1901 and the data serverreceives an eModel in module 1911 after it has been generated in somemanner. One a new eModel has been received, module 1912 extracts a fileheader info data from the eModel file. This module 1912 formats thisinformation and necessary and stores it into a searchable relationaldatabase for use in locating the corresponding eModel at a later date.

Next, the server stores the eModel file into a file storage server inmodule 1913 in order to allow the eModel to be retrieved by end users.The end users locate the eModels by submitting a query to the relationaldatabase to perform a search on the file header info data. The serverreceives the query request in module 1914 which causes the module 1914to query the relational database and return the query results to the enduser. The end user next sends a request for additional queries ifnecessary to identify any eModels of interest.

Once the end user has identifies a desired eModel, the end user sends arequest for an eModel to the data server which is received in module1915. Test module 1916 determines if the end user is permitted access tothe requested eModel. If access is permitted, the eModel is transferredto the end user by module 1917 and the processing ends. If test module1916 determines that access to the eModel is not permitted, the errormessage is returned to the end user by module 1919 and the processingalso ends. One skilled in the art will recognize that alternate userauthentication and access authorization mechanisms may be used to limitaccess to end users when database queries are made as well as wheneModels are accessed without deviating from the spirit and scope of thepresent invention as recited within the attached claims.

FIG. 20 illustrates processing modules used to implement an end userclient computer according to yet another example embodiment of thepresent invention. The end user client computer includes a set ofprocessing modules to provide a window-based user environment tointeract with eModels. The client computer 2001 includes a graphicaluser interface (GUI) module 2012, a command processing and controlmodule 2011, an eModel Item Manipulate module 2010, an eModel storagemodule 2015, an eModel retrieval module 2013, and a data communicationsinterface module 2014. The client computer 2001 may also include localmass storage 2016 to maintain eModels locally as well as on the dataserver 102.

The end user interacts with the client computer 2001 through the GUIinterface module 2012. The end user enters commands using a pointingdevice such as a mouse or trackball and using keyboard commands. Thesecommands are processed by the command processing and control module 2011which send processing requests to the other modules to complete therequested command.

Commands to view an eModel is processed by the eModel retrieval module2013. The eModel retrieval module 2013 obtains a list of the locallyavailable eModels from the eModel storage module 2015 as well ascommunicates with the remote data server 102 using the datacommunications interface module 2014. The end user is presented with alist of available eModels from which an eModel is selected andretrieved. The eModel is retrieved from local storage 2016 if available.If not, the eModel may be transferred from the remote storage. Ifdesired, the retrieved eModel may be stored locally when retrieved fromthe remote server to eliminate the need to down load the eModel in thefuture. Of course, the eModels may also be stored only upon the remotedata server 102 and retrieved when needed.

Once an eModel has been retrieved from data storage, the eModel isprocessed within the eModel Item Manipulate module 2010. This moduledisplays the eModel to the end user. The eModel Item Manipulate module2010 includes an item display module 2021, an item set-up module 2022,and an x-Ray processing module 2023. The item display module 2021displays the eModel graphically to the end user as well as performs theimage display related manipulation operations such as zoom, pan, scroll,and similar visual operations. The item set-up module 2022 allows endusers to obtain measurements of the eModel and modify the eModel tocreate new eModels that may be saved locally using the eModel retrievalmodule 2013. The x-Ray processing module 2023 performs the operationsnecessary to manipulate x-rays as well as combine them with othereModels to create and store composite eModels. One skilled in the artwill recognize that additional manipulation modules may also be used toprocess commands associated with various composite eModels created usingother supported digital image based eModels without deviating from thespirit and scope of the present invention as recited within the attachedclaims.

FIG. 21 illustrates an operational flow for the processing performedwithin an end user client computer according to yet another exampleembodiment of the present invention. The end user process starts 2101and the end user logs into the client computer in module 2110. Thislogging in allows the client system to limit access to eModels if neededwhen the eModels represent confidential data, such as patient data, toonly users who are trusted to use the data appropriately.

Once logged in, an end user is presented with a list of locallyavailable eModels that were obtained in module 2111. Test module 1212determines if a desired eModel is available locally. If test module 1212determines that the desired eModel is not available, the client computerlogs into a remote data server in module 2113 to locate the desiredeModel. A database query used to locate the desired eModel is sent tothe remote server in module 2114 before receiving a list of remotelyavailable eModels. The end user selects the desired eModel and sends arequest for the remotely available eModel to be transmitted to theclient computer in module 2115. The client computer receives the eModelfrom the remote server, stores it locally, and displays it to the userfor manipulation in module 2118.

If test module 2112 determines the desired eModel is locally available,the eModel is retrieved and displayed to the user in module 2117 beforea user manipulates it in module 2118. The end user interactivelymanipulates the eModel as needed in module 2118 to perform the analysisand planning functions that the eModel is useful is assisting. Testmodule 2119 determines if a new eModel has been created that an end userwishes to save locally. If a new eModel is to be saved, module 2120 willsave the newly created eModel locally before the processing ends 2102.If module 2119 determines that a new eModel is not to be saved, theprocessing ends immediately 2102.

FIGS. 22-26 illustrate an implementation of the concepts describedherein pertaining to dental restorations, for example dental crowns anddental implants. An eModel of a proposed dental restoration for apatient can be created in the manner discussed above, typically by adental restoration lab. The restoration eModel can then be combined withan eModel of the remainder (or a finite) portion of the patient's teethat the location where the proposed restoration is to be placed, therebycreating a dental restoration treatment eModel. The treatment eModel canthen be sent to the patient's doctor, who can then view the proposedrestoration relative to neighboring teeth and analyze whether or not therestoration is suitable. If the proposed restoration is acceptable, thedoctor can deliver the treatment eModel to the dental restoration labfor fabrication of the actual dental restoration. If the proposedrestoration is not acceptable, the doctor can take suitable action andnotify the restoration lab that the proposed restoration needs to berevised.

FIG. 22 illustrates a display screen of a doctor's computer or any othercomputer to which the doctor may decide to utilize for analyzingtreatment eModels. The screen displays a proposed dental restoration 10eModel comprising a combination of a crown and a prep site and/orimplant. The restoration 10 eModel is shown in its intended locationrelative to upper 12 and lower 14 eModels of the patient's teeth.Together, the restoration 10 eModel and the eModels 12, 14 form a dentalrestoration treatment eModel. The treatment eModel is typicallygenerated at a location remote from the doctor, for example by a dentalrestoration lab. The treatment eModel is stored within computer readablememory as discussed above. The treatment eModel can then be delivered tothe doctor for analysis of the proposed dental restoration.

Notations can be attached to the treatment eModel as a means ofcommunication between the lab and the doctor. For example, FIG. 22 showsa notation 16 added by the lab commenting on a particular portion of theproposed restoration 10, along with a notation(s) added by the lab 18indicating to the doctor that the proposed restoration 10 is ready to befabricated once the doctor gives the go ahead. A notation(s) 20 can alsobe added by the doctor to comment on any particular portion of theproposed restoration 10. It will be appreciated that more than onedoctor can add notations and the lab can similarly add notations.

Along the top of the display screen are icons 22 that allow the doctorto select different menus of tools for use in displaying and analyzingthe restoration. FIG. 22 shows the file menu tools that open when thedoctor clicks on the “File” icon, permitting the doctor to perform anyof the operations listed under the file menu.

FIG. 23 shows the display screen that results when the doctor clicks onthe “View” icon, permitting the doctor to perform any of the operationslisted under the menus. The operations include the ability to manipulatethe treatment eModel, including changing the view orientation of theeModel (View Controls), as well as selecting the elements of the eModelsthat are displayed (View Objects) and selecting tools (View Tools) toaid in analyzing the proposed restoration 10.

FIG. 24 shows the display screen that results when the doctor clicks onthe “Notes” icon, permitting the doctor to perform any of the operationslisted under the menus. In addition to View Controls and View Objectsmenus, the doctor is presented with a Notation Tools menu that allowsthe doctor to add, remove, move and edit notations 20 on the treatmenteModel. Notations allow the doctor to comments on areas of the treatmenteModel that may need to be altered to optimize the restoration, so thatwhen the treatment eModel with attached notation is sent back to thelab, the lab technician knows which areas of the treatment eModel mayneed to be revised and by how much.

FIG. 25 shows the display screen that results when the doctor clicks onthe “Tools” icon, permitting the doctor to perform any of the operationslisted under the menus. In addition to View Controls and View Objectsmenus, the doctor is presented with a Colormap Tools menu that allowsthe doctor to analyze certain parameters relating to the interactionbetween the proposed restoration and neighboring teeth, and parametersof the proposed restoration itself. For example, the Colormap Tools menuenables the doctor to analyze occlusal contact, interproximal contact,thickness of the crown, and the thickness between the bottom of thecrown and the top of the prep site or implant.

The Colormap Tools menu allows the doctor to display the locations ofocclusal contact and the degree of contact as part of his analysis, asshown in FIG. 26, with different colors being used to representdiffering degrees of contact, as indicated in the displayed legend.

FIG. 27 illustrates an operational flow of an exemplary dentalrestoration treatment process using the dental restoration eModel. Theprocess starts 30 and the treatment eModel is opened and displayed 32 bythe doctor after the treatment eModel has been sent to the doctor by thelab. The doctor opens 34 the desired analysis tools and analyzes 36 theproposed restoration to determine whether the proposed restoration isacceptable. If the proposed restoration is not acceptable, or the doctorsimply wants to send a message to the lab, the doctor opens 38 thenotation tool and clicks on “Add a Note” 40 and enters the text of themessage. The doctor then optionally clicks on “Add Indicator Line” todraw a line to the area of the treatment eModel to which the noteapplies. If the note is not directed to a specific area of the treatmenteModel, then an indicator line may not be necessary. Once all notes havebeen added and the doctor has completed the analysis, the doctor clickson “Send ICON model to Lab” in the file menu to send the treatmenteModel with the attached notes to the lab for consideration and revisionof the eModel. The doctor can also save the treatment eModel, includingthe notes, on a suitable computer readable storage medium for later use.Once the eModel is sent back to the lab, that stage of the process ends46.

The process in FIG. 27 can be iterative, in which case the lab can sendthe revised treatment eModel back to the doctor once revisions have beenmade for approval by the doctor. The doctor can make a further analysisand, if necessary, suggest further modifications, or, if no additionalchanges are necessary, approve the restoration for subsequentfabrication.

The software program (and programming steps) implementing the presentinvention is a single executable file stored and implemented by the enduser's (e.g., the doctor) 110-113 computers. The program is written in Cand C⁺⁺. The program QT is utilized to make the Microsoft Windows callsto enable higher level/simplified coding. The program can alternativelybe implemented as a browser based web service (for example using Javascripts).

FIG. 2 preferably illustrates an example of a suitable operatingenvironment 121 in which the invention may be implemented. The operatingenvironment is only one example of a suitable operating environment 121and is not intended to suggest any limitation as to the scope of use orfunctionality of the invention. Other well known computing systems,environments, and/or configurations that may be suitable for use withthe invention include, but are not limited to, personal computers,server computers, held-held or laptop devices, multiprocessor systems,microprocessor-based systems, programmable consumer electronics, networkPCs, minicomputers, mainframe computers, distributed computingenvironments that include any of the above systems or devices, and thelike.

The invention may also be described in the general context ofcomputer-executable instructions, such as program modules, executed byone or more computers or other devices. Generally, program modulesinclude routines, programs, objects, components, data structures, etc.that perform particular tasks or implement particular abstract datatypes. Typically the functionality of the program modules may becombined or distributed in desired in various embodiments.

A network server 121 typically includes at least some form of computerreadable media. Computer readable media can be any available media thatcan be accessed by the network server 110. By way of example, and notlimitation, computer readable media may comprise computer storage mediaand communication media. Computer storage media includes volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information such as computer readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, BC-ROM, digital versatile disks (DVD)or other optical storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or any other mediumwhich can be used to store the desired information and which can beaccessed by the network server 110.

Communication media typically embodies computer readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of any ofthe above should also be included within the scope of computer readablemedia.

While the above embodiments of the present invention describe a networkbased processing system providing processing services to remote clients,one skilled in the art will recognize that the various distributedcomputing architectures may be used to implement the present inventionas recited within the attached claims. It is to be understood that otherembodiments may be utilized and operational changes may be made withoutdeparting from the scope of the present invention.

The foregoing description of the exemplary embodiments of the inventionhas been presented for the purposes of illustration and description.They are not intended to be exhaustive or to limit the invention to theprecise forms disclosed. Many modifications and variations are possiblein light of the above teaching. It is intended that the scope of theinvention be limited not with this detailed description, but rather bythe claims appended hereto. Thus the present invention is presentlyembodied as a method, apparatus, computer storage medium or propagatedsignal containing a computer program for providing a method, apparatus,and article of manufacture for providing a distributed computing systemfor the creation and distribution of electronic models of objects.

1. A method for providing electronic delivery of an electronic modelimage of a dental restoration treatment, the method comprising:generating an electronic model image of a proposed dental restorationtreatment; storing the electronic model image within computer readablememory of a server-based computing system; delivering the electronicmodel image to a doctor having a remote client computer over adistributed communications network; and displaying the electronic modelimage upon the remote client computer and performing analysis of theelectronic model image.
 2. The method of claim 1, further comprisingattaching a notation to the electronic model image that is displayedupon the remote client computer.
 3. The method of claim 2, furthercomprising delivering the electronic model image with attached notationto a dental restoration laboratory.
 4. The method of claim 1, furthercomprising manipulating the displayed electronic model image upon theremote client computer.
 5. The method of claim 1, further comprisingstoring the electronic model image within computer readable memory ofthe remote client computer.
 6. A method of dental restoration treatment,comprising: displaying an electronic model image of a proposed dentalrestoration treatment upon a display device; performing an analysis ofthe electronic model image to determine whether or not the proposeddental restoration treatment is appropriate; and attaching a notation tothe electronic model image that is displayed.
 7. The method of claim 6,further comprising delivering the electronic model image with attachednotation to a dental restoration laboratory over a distributedcommunications network.
 8. The method of claim 6, wherein the analysiscomprises manipulating the displayed electronic model image.
 9. Themethod of claim 8, wherein manipulating comprises changing theorientation of the displayed electronic model image.
 10. The method ofclaim 8, wherein the analysis comprises determining and displaying theoccurrence of occlusal contact with a dental restoration of the proposeddental restoration treatment.
 11. The method of claim 8, wherein theanalysis comprises determining the occurrence of interproximal contactwith a dental restoration of the proposed dental restoration treatment.12. The method of claim 6, further comprising storing the electronicmodel image with the attached notation within computer readable memory.